Re: Local replication slot does not exist after initial sync

Re: Local replication slot does not exist after initial sync start_replication slot START_REPLICATION SLOT “timescaledb_1” 5299D000000 TIMELINE 50 20:42:15 UTC ,app start replication slot postgres Limiting replication slot size can save you primary database server from abrupt shutdown Learn here how to protect your production systems

start replication slot postgres start_replication7 start_replication(Connection::connection(), ReplicationSlot ReplicationSlot: the name of the replication slot to stream changes from

greatblue slot You can verify this by setting the slotName extra connection attribute to the name of this logical replication slot For more information, see Extra This section describes the logical replication protocol, which is the message flow started by the START_REPLICATION SLOT slot_name LOGICAL replication command